C-CDA to FHIR System API - Application

Importing Templates into Anypoint Studio

1. In Studio, click the Exchange X icon in the upper left of the taskbar.
2. Log in with your Anypoint Platform credentials.
3. Search for the template.
4. Click Open.

Running Templates in Anypoint Studio

After you import your template into Studio, follow these configuration steps to run it.

C-CDA to FHIR Converter Application Configuration

The application requires a few things to be configured, mainly the system API connection information. Configure them in the properties file located in the config/properties folder.

• mule.env is the environment where the application is to be deployed. For a studio deployment, the recommended mule.env value is local.
• mule.encryptionKey is the encryption key for securing sensitive properties.

Please refer to the attached link on how to secure the configuration properties.

HTTPS Configuration

• https.host — sets the service host interface. It should be configured in config-<mule.env>.yaml file. (Defaults to 0.0.0.0 for all interfaces).
• https.port — sets the HTTPS service port number. It should be configured in config-<mule.env>.yaml file. (Default 8082).
• TLS Configuration - Keystore properties setup:
  • keystore.alias - sets the alias to the keystore. It should be configured in config-<mule.env>.yaml file.
  • keystore.path - sets the path to the key file. Key should be available in /src/main/resources/keystore. It should be configured in config-<mule.env>.yaml file.
  • keystore.keypass — sets keystore keypass to support HTTPS operation. It should be encrypted and configured in config-secured-<mule.env>.yaml file.
  • keystore.password— sets keystore password to support HTTPS operation. It should be encrypted and configured in config-secured-<mule.env>.yaml file.

Please refer to the attached link on how to generate the Keystore.

Tested and verified

This solution was developed and tested on Anypoint Studio 7.15 and Mule Runtime 4.4.0.

Assumptions and Constraints

• For all DateTime fields, if the timezone is not specified then it is assumed to be a local (server) time and converts to Zulu.
• The narrative (text.div) element inside the FHIR JSON response is an XHTML fragment, which is restricted to support only basic HTML formatting elements and attributes. As a result, this application applies XSLT for refining the narrative.div into a fully supported XHTML format.Users have the option to alter the XSLT found within the Mule Xslt Transform activity, called xslt-cleanup-ccda, inside the ccda-to-fhir-sys-api.xml.

Running it

1. Right-click the template project folder.
2. Hover your mouse over 'Run as'.
3. Click Mule Application (configure).
4. Inside the dialog, select Environment and set the variable mule.env to the appropriate value (e.g., dev or local).
5. Inside the dialog, select Environment and set the variable mule.encryptionKey to the property encryption key that you used to encrypt your secure properties.
6. Inside the dialog, go to 'Clear Application Data' select 'always' radio button.
7. Click Run.

Deployment instructions for CloudHub using provided scripts

Ensure the Maven profile CloudHub-DEV has been properly configured in your settings.xml file. Reference can be found by downloading the Accelerator Common Resources asset. Additional instructions are available in the Getting Started with MuleSoft Accelerators - Build Environment guide.

Update the config-<env>.yaml properties appropriately and then use one of the following scripts to deploy the application to Cloud Hub:

• packageDeploy.sh or deployOnly.sh (Mac/Linux)
• packageDeploy.cmd or deployOnly.cmd (Windows)

Test the template

• Use Advanced Rest Client or Postman to send a request over HTTPS. The template includes a Postman collection in the src/test/resources folder. Update the collection variable(s) after successful import.